On Mon, 24 Sep 2001 08:39:18 -0500, "Bob H." <omn### [at] msncom>
wrote:
> "W?odzimierz ABX Skiba" <abx### [at] babilonorg> wrote in message
> news:h9utqt0r7aer5md5md2ge3kpu39131k51e@4ax.com...
> >
> > Please parse below and look at the output where it stops and what is
> > the output. I didn't found anything within 6.1.7.1 and 6.1.7.3 what
> > could explain this
>
> I don't see a problem, you just need to use comma separation.

but I see the problem

I found this playing with Parse_String macro

I just generated macro with it this way for example

Parse_String(concat(
  "#macro Name(Params)",
    :   // here are lines with content of macro
    :
  "#end"
))

and sometimes I forgot to add comma after lines of string
and it was parsed ok during concatenation but during Parse_String it
behave  unexpected
I found that it lost some lines

I don't think there must be possibility to not use comma
I just think there should be at least warning that comma required

> concat() is
> obviously ignoring the quotes when without commas which turns the "2" into
> nothing seen.  So that error of the last example is seeing just a 1 with
> nothing to concatenate onto it.

I don't say about last line but about all without first !!!
Question is: why it wasn't reported during parse ? Second string
(without comma) is always invisible. Third is visible.

> Looking at the Scene Help I don't see an example without commas.

Perhaps I missed something but have you seen example without commas
for sphere{x 1} or triangle{x y z} ?


ABX

Post a reply to this message